Skip to content

Conversation

@chtruong814
Copy link
Contributor

Add initial nemo-lm boilerplate

Will work on ensuring the CI tests run in the next PR.

Signed-off-by: Charlie Truong <[email protected]>
Signed-off-by: Charlie Truong <[email protected]>
@chtruong814 chtruong814 requested review from ko3n1g and thomasdhc May 23, 2025 21:38
Signed-off-by: Charlie Truong <[email protected]>
Signed-off-by: Charlie Truong <[email protected]>
@chtruong814 chtruong814 changed the title Add initial nemo-lm boilerplate ci: Add initial nemo-lm boilerplate May 23, 2025
Copy link
Contributor

@ko3n1g ko3n1g left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the initial PR! Great work so far, just some small notes and observations

Comment on lines +13 to +15
# limitations under the License.
name: ~Build container template
on:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a copy-paste error

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah yup.

Comment on lines +24 to +25
--mount=type=bind,source=requirements,target=/workspace/requirements \
pip install --no-build-isolation --no-cache-dir '.[all]'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'll need another layer with devel version of Mcore and NeMo-Run

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any reason why we shouldn't just update the requirements file to install from a commit if necessary?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At least for Mcore, I feel that one we could and should be pinning by commit in the requirements file. No different than what we're doing in the current NeMo repo.

For NeMo-Run, maybe we should just be pinning that as well? In both cases, I'm not sure we care too much about staying on main and prefer more stability anyway.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When a requirements file specifies a VCS/git package, the package itself cannot be published to PyPi anymore. We would need to update the requirements-file prior to pushing to PyPi. I was briefly considering to hack around this with extra_requires ([dev]), but I think those fall under the same constraint

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah gotcha. Ok, I'll add that additional layer. Will add build args to enable busting the cache as needed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ko3n1g I updated to add that extra layer in the docker file. Afterwards we can check in with what mcore commits at least the nemo-lm team was developing against. Please take a look when you get a chance.

Copy link
Contributor

@ko3n1g ko3n1g left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome! Please remember to update the test-template action. Other LGTM, approving now to unblock the team

@chtruong814 chtruong814 merged commit d71db9a into main May 27, 2025
3 checks passed
yaoyu-33 pushed a commit that referenced this pull request Jul 10, 2025
@ko3n1g ko3n1g deleted the chtruong/initial-ci branch August 14, 2025 08:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants